Scheduling Request Triggering in a Wireless Device

ABSTRACT

A wireless device receives configuration parameters indicating a mapping restriction, of a plurality of mapping restrictions, of a logical channel to one or more radio resource types of a plurality of radio resource types. A buffer status report is triggered based on uplink data becoming available. An uplink grant indicating radio resources of a radio resource type of the plurality of radio resource types is received. A scheduling request is triggered in response to: the triggering the buffer status report; and the radio resource type not being of at least one first radio resource type, of the plurality of radio resource types, determined based on the plurality of mapping restrictions. The wireless device transmits the scheduling request.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of Ser. No. 15/497,197, filed Apr.25, 2017, which claims the benefit of U.S. Provisional Application No.62/327,265, filed Apr. 25, 2016 and U.S. Provisional Application No.62/327,312, filed Apr. 25, 2016, which are hereby incorporated byreference in their entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is an example diagram depicting OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 4 is an example block diagram of a base station and a wirelessdevice as per an aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10 is an example diagram depicting a downlink burst as per anaspect of an embodiment of the present disclosure.

FIG. 11 is an example diagram depicting example logical channels andexample mapping restrictions as per an aspect of an embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation ofcarrier aggregation. Embodiments of the technology disclosed herein maybe employed in the technical field of multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCIdownlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LAA licensed assisted access

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAItracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentinvention. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) mayconsist of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a carrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to aspects of an embodiments, transceiver(s) may be employed.A transceiver is a device that includes both a transmitter and receiver.Transceivers may be employed in devices such as wireless devices, basestations, relay nodes, and/or the like. Example embodiments for radiotechnology implemented in communication interface 402, 407 and wirelesslink 411 are illustrated are FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to various aspects of an embodiment, a network may include amultitude of base stations, providing a user plane PDCP/RLC/MAC/PHY andcontrol plane (RRC) protocol terminations towards the wireless device.The base station(s) may be interconnected with other base station(s)(for example, interconnected employing an X2 interface or an Xninterface). Base stations may also be connected employing, for example,an S1 interface to an EPC. For example, base stations may beinterconnected to the MME employing the S1-MME interface and to the S-G)employing the S1-U interface. The S1 interface may support amany-to-many relation between MMEs/Serving Gateways and base stations. Abase station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink,the carrier corresponding to the PCell may be the Uplink PrimaryComponent Carrier (UL PCC). Depending on wireless device capabilities,Secondary Cells (SCells) may be configured to form together with thePCell a set of serving cells. In the downlink, the carrier correspondingto an SCell may be a Downlink Secondary Component Carrier (DL SCC),while in the uplink, it may be an Uplink Secondary Component Carrier (ULSCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may apply,for example, to carrier activation. When the specification indicatesthat a first carrier is activated, the specification may also mean thatthe cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present disclosure.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC_CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the disclosure.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise two subsets: the Master CellGroup (MCG) containing the serving cells of the MeNB, and the SecondaryCell Group (SCG) containing the serving cells of the SeNB. For a SCG,one or more of the following may be applied. At least one cell in theSCG may have a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), may be configured with PUCCHresources. When the SCG is configured, there may be at least one SCGbearer or one Split bearer. Upon detection of a physical layer problemor a random access problem on a PSCell, or the maximum number of RLCretransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG may be stopped, anda MeNB may be informed by the UE of a SCG failure type. For splitbearer, the DL data transfer over the MeNB may be maintained. The RLC AMbearer may be configured for the split bearer. Like a PCell, a PSCellmay not be de-activated. A PSCell may be changed with a SCG change (forexample, with a security key change and a RACH procedure), and/orneither a direct bearer type change between a Split bearer and a SCGbearer nor simultaneous configuration of a SCG and a Split bearer may besupported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied. The MeNB may maintain theRRM measurement configuration of the UE and may, (for example, based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE. Upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so).For UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB. The MeNB and the SeNBmay exchange information about a UE configuration by employing RRCcontainers (inter-node messages) carried in X2 messages. The SeNB mayinitiate a reconfiguration of its existing serving cells (for example, aPUCCH towards the SeNB). The SeNB may decide which cell is the PSCellwithin the SCG. The MeNB may not change the content of the RRCconfiguration provided by the SeNB. In the case of a SCG addition and aSCG SCell addition, the MeNB may provide the latest measurement resultsfor the SCG cell(s). Both a MeNB and a SeNB may know the SFN andsubframe offset of each other by OAM, (for example, for the purpose ofDRX alignment and identification of a measurement gap). In an example,when adding a new SCG SCell, dedicated RRC signaling may be used forsending required system information of the cell as for CA, except forthe SFN acquired from a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprises aPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to an embodiment, initial timing alignment may be achievedthrough a random access procedure. This may involve a UE transmitting arandom access preamble and an eNB responding with an initial TA commandNTA (amount of timing advance) within a random access response window.The start of the random access preamble may be aligned with the start ofa corresponding uplink subframe at the UE assuming NTA=0. The eNB mayestimate the uplink timing from the random access preamble transmittedby the UE. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The UE may determine the initial uplink transmissiontiming relative to the corresponding downlink of the sTAG on which thepreamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to variousaspects of an embodiment, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, (for example, at least one RRC reconfigurationmessage), may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of thepTAG. When an SCell is added/configured without a TAG index, the SCellmay be explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (for example, to establish, modify and/orrelease RBs, to perform handover, to setup, modify, and/or releasemeasurements, to add, modify, and/or release SCells). If the receivedRRC Connection Reconfiguration message includes the sCellToReleaseList,the UE may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the UE mayperform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH may only be transmitted onthe PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timermay be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. This mayrequire not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum may therefore be needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it may be beneficialthat more spectrum be made available for deploying macro cells as wellas small cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, may be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA may offer an alternative for operators to make use ofunlicensed spectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAmay utilize at least energy detection to determine the presence orabsence of other signals on a channel in order to determine if a channelis occupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs, time & frequency synchronizationof UEs, and/or the like.

In an example embodiment, a DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

An LBT procedure may be employed for fair and friendly coexistence ofLAA with other operators and technologies operating in an unlicensedspectrum. LBT procedures on a node attempting to transmit on a carrierin an unlicensed spectrum may require the node to perform a clearchannel assessment to determine if the channel is free for use. An LBTprocedure may involve at least energy detection to determine if thechannel is being used. For example, regulatory requirements in someregions, for example, in Europe, may specify an energy detectionthreshold such that if a node receives energy greater than thisthreshold, the node assumes that the channel is not free. While nodesmay follow such regulatory requirements, a node may optionally use alower threshold for energy detection than that specified by regulatoryrequirements. In an example, LAA may employ a mechanism to adaptivelychange the energy detection threshold. For example, LAA may employ amechanism to adaptively lower the energy detection threshold from anupper bound. Adaptation mechanism(s) may not preclude static orsemi-static setting of the threshold. In an example a Category 4 LBTmechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies, no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (for example, LBT withoutrandom back-off) may be implemented. The duration of time that thechannel is sensed to be idle before the transmitting entity transmitsmay be deterministic. In an example, Category 3 (for example, LBT withrandom back-off with a contention window of fixed size) may beimplemented. The LBT procedure may have the following procedure as oneof its components. The transmitting entity may draw a random number Nwithin a contention window. The size of the contention window may bespecified by the minimum and maximum value of N. The size of thecontention window may be fixed. The random number N may be employed inthe LBT procedure to determine the duration of time that the channel issensed to be idle before the transmitting entity transmits on thechannel. In an example, Category 4 (for example, LBT with randomback-off with a contention window of variable size) may be implemented.The transmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by a minimumand maximum value of N. The transmitting entity may vary the size of thecontention window when drawing the random number N. The random number Nmay be employed in the LBT procedure to determine the duration of timethat the channel is sensed to be idle before the transmitting entitytransmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (for example, by using different LBT mechanismsor parameters), since the LAA UL may be based on scheduled access whichaffects a UE's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme include, but are not limited to,multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. A UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, a UL transmission burst may be defined from a UEperspective. In an example, a UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

In an example embodiment, in an unlicensed cell, a downlink burst may bestarted in a subframe. When an eNB accesses the channel, the eNB maytransmit for a duration of one or more subframes. The duration maydepend on a maximum configured burst duration in an eNB, the dataavailable for transmission, and/or eNB scheduling algorithm. FIG. 10shows an example downlink burst in an unlicensed (e.g. licensed assistedaccess) cell. The maximum configured burst duration in the exampleembodiment may be configured in the eNB. An eNB may transmit the maximumconfigured burst duration to a UE employing an RRC configurationmessage.

The wireless device may receive from a base station at least one message(for example, an RRC) comprising configuration parameters of a pluralityof cells. The plurality of cells may comprise at least one license celland at least one unlicensed (for example, an LAA cell). Theconfiguration parameters of a cell may, for example, compriseconfiguration parameters for physical channels, (for example, a ePDCCH,PDSCH, PUSCH, PUCCH and/or the like).

In an example, an eNB and/or UE may support a plurality of radioresource types. In an example, various radio resource types may beconfigured with various TTIs and/or numerologies. In an example, a firstradio resource type may operate using at least one first TTI/numerologyand a second radio resource type may operate using at least one secondTTI/numerology. In an example, various resource types may operate indifferent frequencies or frequency bands. In an example, a first radioresource type may operate on one or more licensed cells and a secondradio resource type may operate on one or more unlicensed cells. Anexample may use a combination of various features to determine a radioresource type, e.g. frequency, TTI/numerology, frequency band type, etc.Some of the example embodiments are provided for licensed and unlicensed(e.g. LAA cells) radio resource types. These examples may equally applywhen other radio resource types are implemented, e.g., based onTTI/numerology.

In an example, an eNB and/or UE may support a plurality of radioresource types. In an example, various radio resource types may beconfigured with various TTIs and/or numerologies. In an example, a firstradio resource type may operate using at least one first TTI/numerologyand a second radio resource type may operate using at least one secondTTI/numerology. In an example, various resource types may operate indifferent frequencies or frequency bands. In an example, a first radioresource type may operate on one or more licensed cells and a secondradio resource type may operate on one or more unlicensed cells. Anexample may use a combination of various features to determine a radioresource type, e.g. frequency, TTI/numerology, frequency band type, etc.Some of the example embodiments are provided for licensed and unlicensed(e.g. LAA cell) radio resource types. These examples may equally applywhen other radio resource types are implemented, e.g., based onTTI/numerology. In an example, one, two, three or more radio resourcetypes may be defined.

In downlink, an eNB may decide which data of which radio bearer/logicalchannel is mapped to which radio resource type in a plurality of radioresource types (e.g. licensed/unlicensed carriers, different subcarriersand subframe types/durations, different frequencies). For example, theeNB may consider sending data in the licensed carrier if the unlicensedcarrier is unstable, congested, and/or has poor quality e.g. due tointerference. Data transmission may be limited to a certain radioresource type depending on (SRB/DRB)/logical channel configuration. QoSmay be supported employing radio bearers in the air interface.

In an example embodiment, the radio environment in a first radioresource type (e.g. unlicensed spectrum) may be different compared withthat a second radio resource type (e.g. on licensed spectrum). Inunlicensed spectrum, there may be various sources for interference whichis outside the control of the operator, e.g., other RATs (e.g. WiFi)and/or LAA-capable eNB/UEs of other operators. The unlicensed carriermay experience high interference. LBT may be supported to meetregulatory requirements. This may delay packet transmission and mayimpact QoS of some bearers, e.g. latency requirements might not besatisfied. Example such bearers may be voice, real time gaming, and/orSRB.

Bearer/logical channel may be configured by an eNB as to whether theymay be only served via a first radio resource type (e.g. LAA cells) orwhether they may only be served via a second radio resource type (e.g.licensed cells) or both first and second radio resource types. In anexample, the network/eNB may configure per bearer (SRB/DRB) whether itcan be offloaded to a first radio resource type (e.g. LAA cells) and/ora second radio resource type (e.g. licensed cells). In an example, thenetwork/eNB may configure per logical channel whether it can beoffloaded to a first radio resource type (e.g. LAA cells) and/or asecond radio resource type (e.g. licensed cells).

In an example embodiment, on an LAA carrier, packets may not be receivedwithin some time limit for example because of LBT for UL transmission.Delay sensitive bearers/logical channels (e.g. voice, RRC signaling) maybe configured not to be transmitted over the UL LAA SCells. Abearer/logical channel may be configured to use the UL grants only forUL licensed serving cells. Otherwise, it may use the UL grants fromlicensed and/or unlicensed cells.

In an example embodiment, the Logical Channel Prioritization proceduremay be applied when a new transmission is performed by a UE. In orderfor the UE MAC to differentiate whether a new transmission is on a UL ofa first radio resource type (e.g. LAA cells) or on a UL of a secondradio resource type (e.g. licensed cells), layer one (PHY) may indicatefor an UL grant whether the uplink grant is for a first radio resourcetype (e.g. LAA cells) or a second radio resource type (e.g. licensedcells). A base station may transmit to a wireless device an uplink grantindicating resource blocks and radio resource type for uplinktransmission of one or more uplink transport blocks.

In an example embodiment, for a new transmission on an UL LAA SCell, theUE MAC entity may apply the logical channel prioritization procedure onthe logical channels configured by RRC that may use the UL grants forboth the UL LAA SCells and the licensed UL serving cells. The logicalchannels that can only use the UL grants for the licensed UL servingcells will not be considered for the new transmission on a UL LAA SCell.

In an example, the MAC UE entity may differentiate whether a newtransmission is on a first radio resource type (e.g. LAA cells) or on asecond radio resource type (e.g. licensed cells) and use thisinformation to apply logical channel prioritization procedure accordingto which logical channels can use only a first or second radio resourcetypes or can use both first radio resource type and second radioresource type.

In an example embodiment, per bearer, per logical channel, and/or perlogical channel group configuration may be considered. The eNB mayconfigure logical channel to radio resource type (e.g. licensed/LAAcell) restrictions per bearer, per logical channel, and/or per logicalchannel group.

SRBs may be restricted to only be sent on carriers in a first radioresource type or SRBs may be sent on carriers in a second radio resourcetype or both. The eNB may indicate whether bearers/logical channels canbe sent over a first radio resource type. This may apply also for SRBsand it may be possible to configure the UE to send SRBs on second radioresource type.

In order for the eNB to know what UL grant to provide (for first orsecond radio resource types), the UE may inform the eNB which bearershave buffers comprising UL data. A UE sends Buffer Status Reporting(BSR) to the eNB. This Buffer Status report includes logical channelgroup ID and its corresponding UL buffer status. The 2-bit logicalchannel group ID is eNB configured ID to group the logical channels ofthe same or similar QoS in one group ID. This is to allow the eNB toperform inter and intra UE prioritization for allocating the ULresources. In an example, this LCGID may also be reused or extended totake into account the logical channels that can use the UL grants onlyfor the UL via a first radio resource type or a second radio resourcetype and the logical channels that can use the UL grants via both firstand second radio resource types.

In an example embodiment, LCGID#0 may be used for RRC signaling anddelay sensitive services (e.g. voice, streaming video). If a UE'sserving cell contains activated UL LAA SCell and the BSR indicates onlybuffer status from LCGID#0, the eNB may not allocate UL grants from theLAA SCell to the UE. In an example, the UL resources for PUSCH may beclassified as licensed carrier and unlicensed carrier. For UL resourcesfor PUSCH in licensed carrier, LCGID#0 may be considered higher prioritythan other LCGIDs by the eNB scheduler. Among UEs with LCGID#0, it maybe scheduled like in the legacy (e.g. round-robin).

In an example embodiment, the LCGID may be used by the eNB todifferentiate between buffer status on logical channels that can use ULgrants of the first radio resource type and the buffer status on logicalchannels that can use UL grants for the second radio resource type, andthe buffer status on logical channels that can use UL grants for boththe first and second radio resource types.

In an example embodiment, information element unlicensed-Prohibited maybe employed to indicate that a LC, bearer, and/or LCG is prohibited fortransmission on an LAA cell. This variable may be a binary variable. Ifthe variable is not present, it may indicate that the corresponding datacan be routed on licensed or unlicensed cells.

FIG. 11 shows an example routing (mapping) restriction according to anexample embodiment. In an example, a routing (mapping) restrictioninformation element may include one or more parameters indicating one ormore radio resource types that a logical channel or a logical channelgroup can be mapped to. The UE may employ the routing (mapping)restriction information element to transmit data of the logical channelsusing one or more transport blocks and via one or more radio resourcetypes indicated in the routing (mapping) restriction.

Example configuration for routing restrictions per bearer may beimplemented. The IE RadioResourceConfigDedicated may be used tosetup/modify/release RBs, to modify the MAC main configuration, tomodify the SPS configuration and to modify dedicated physicalconfiguration.

Example configuration for routing restrictions per logical channel maybe implemented. The IE LogicalChannelConfig may be used to configure thelogical channel parameters. A logical channel configuration may compriseone or more of the following parameters. bucketSizeDuration: Bucket SizeDuration for logical channel prioritization (e.g., value inmilliseconds, e.g. value ms50 corresponds to 50 ms, ms100 corresponds to100 ms and so on). logicalChannelGroup: mapping of logical channel tological channel group for BSR reporting. logicalChannelSR-Mask:controlling SR triggering on a logical channel basis when an uplinkgrant is configured. logicalChannelSR-Prohibit: e.g. value True mayindicate that the logicalChannelSR-ProhibitTimer is enabled for thelogical channel. E-UTRAN (optionally) configures the field (e.g.indicates value TRUE) if logicalChannelSR-ProhibitTimer is configured.prioritisedBitRate: Prioritized Bit Rate for logical channelprioritization (e.g. value in kilobytes/second, value kBps0 correspondsto 0 kB/second, kBps8 corresponds to 8 kB/second, kBps16 corresponds to16 kB/second and so on). Infinity may be the applicable value for SRB1and SRB2. priority: Logical channel priority (e.g. value is an integer).SRmask: the field is optionally present if ul-SpecificParameters ispresent, need OR; otherwise it may not be present. Some of the aboveexample parameters may be optional. Other example parameters may beconfigured for a logical channel.

Example configuration for routing restrictions per logical channel groupmay employ the example configuration per logical channel. The eNB mayconsider the routing restrictions into account when the eNB configures arouting restriction for a logical channel so that one or more logicalchannels in a given logical channel group have the same routingrestrictions. For example, two logical channels with two differentrouting restrictions may not be configured in the same logical channelgroup. This may enable the eNB to assume that data belonging to the samelogical channel group have the same routing limitations. When a BSR isreported for a logical channel group, the eNB may employ the BSR toproperly allocate resources on one or more LAA cells, one or morelicensed cells, or both licensed and unlicensed cells. The eNB mayemploy other parameters such as load, congestion, and channel quality toallocate resources on different cells. A mapping (routing) restrictionof a logical channel to one or more radio resource types indicates thatthe logical channel can employ the one or more radio resource types fortransmission of uplink and/or downlink data.

In an example embodiment, the eNB may assign a routing restriction to alogical channel group comprising one or more logical channels. Forexample, the eNB may configure logical channel group 0 to be transmitted(routed) on a second radio resource type (e.g. licensed cells). Forexample, the eNB may configure logical channel group 1 to be transmitted(routed) on a first and/or second radio resource types (e.g. licensedand/or LAA cells) depending on resource availability. The eNB maytransmit at least one RRC message to configure a plurality of cells. Theat least one RRC message may comprise one or more parameters toassociate a routing (mapping) restriction to a logical channel groupnumber. For example, at least one RRC message may comprise a sequence ofparameters, and an element in the sequence may comprise a parameter forrouting restriction and a logical channel group number (or a logicalchannel number). For example, at least one RRC message may comprise asequence of parameters, and an element in the sequence may comprise aparameter for routing restriction. The parameters may be orderedaccording to the logical channel group ID (or logical channel ID).

The eNB may transmit one or more RRC message to configure a plurality ofcells and one or more radio resource types (e.g. licensed cell and oneor more LAA cells). The one or more RRC messages may compriseMAC-MainConfig. The IE MAC-MainConfig may be used to specify the MACmain configuration for signaling and data radio bearers. MAC mainconfiguration parameters may be configured independently per Cell Group(e.g. MCG or SCG).

In an example, MAC-MainConfig information element may comprise one ormore of the following parameters. periodicBSR-Timer: Timer for BSRreporting (e.g. value in number of sub-frames, e.g. value sf10corresponds to 10 sub-frames, sf20 corresponds to 20 sub-frames and soon). retxBSR-Timer: Timer for BSR reporting (e.g. value in number ofsub-frames, value sf640 corresponds to 640 sub-frames, sf1280corresponds to 1280 sub-frames and so on).logicalChannelSR-ProhibitTimer: Timer used to delay the transmission ofan SR for logical channels enabled by logicalChannelSR-Prohibit (e.g.value sf20 corresponds to 20 subframes, sf40 corresponds to 40subframes, and so on).

The UE may transmit UE-EUTRA-Capability to the eNB to indicate one ormore UE capability to the eNB. The IE UE-EUTRA-Capability is used toconvey the E-UTRA UE Radio Access Capability Parameters, and the FeatureGroup Indicators for mandatory features to the network. The IEUE-EUTRA-Capability is transferred in E-UTRA or in another RAT. Anexample capability parameter is shown below:MAC-Parameters-r12::=SEQUENCE {logicalChannelSR-ProhibitTimer-r12:ENUMERATED {supported} OPTIONAL, longDRX-Command-r12:ENUMERATED{supported} OPTIONAL}. In an example, logicalChannelSR-ProhibitTimer:Indicates whether the UE supports the logicalChannelSR-ProhibitTimer.

Example Buffer Status Report (BSR) MAC control elements comprise: ShortBSR and Truncated BSR format: one LCG ID field and one correspondingBuffer Size field; and Long BSR format: four Buffer Size fields,corresponding to LCG IDs #0 through #3. Other BSR example formats may bedefined. The BSR formats may be identified by MAC PDU subheaders withLCIDs. Example fields LCG ID and Buffer Size are defined as follow: LCGID: The Logical Channel Group ID field identifies the group of logicalchannel(s) which buffer status is being reported. The length of thefield may be 2 bits; buffer Size: The buffer size field identifies thetotal amount of data available across logical channels of a logicalchannel group after MAC PDUs for the TTI have been built. The amount ofdata may be indicated in number of bytes. It may include data that isavailable for transmission in the RLC layer and in the PDCP layer. Thesize of the RLC and MAC headers may not be considered in the buffer sizecomputation. The length of this field may be 6 bits. An example shortBSR and/or truncated BSR MAC control element may comprise of LCG IDfield and buffer size field. An example, long BSR MAC control elementmay comprise of four buffer size fields for four logical channel groups.Buffer size field value may indicate the amount of data in a logicalchannel or logical channel group.

In an example, Sidelink BSR and truncated Sidelink BSR MAC controlelements comprises of one destination index field, one LCG ID field andone corresponding Buffer Size field per reported target group. TheSidelink BSR MAC control elements may be identified by MAC PDUsubheaders with LCIDs as. They may have variable sizes. For an includedgroup, example fields are defined as follows. Destination Index: TheDestination Index field identifies the ProSe Destination. The length ofthis field is 4 bits. The value is set to the index of the destinationreported in destinationInfoList and if destinationInfoListUC is alsoreported, the value is indexed sequentially. LCG ID: The Logical ChannelGroup ID field identifies the group of logical channel(s) which bufferstatus is being reported. The length of the field may be 2 bits. BufferSize: The Buffer Size field identifies the total amount of dataavailable across logical channels of a LCG of a ProSe Destination afterMAC PDUs for the TTI have been built. The amount of data is indicated innumber of bytes. It may include data that is available for transmissionin the RLC layer and in the PDCP layer. The size of the RLC and MACheaders are not considered in the buffer size computation. The length ofthis field may be 6 bits. Buffer Sizes of LCGs may be included indecreasing order of the highest priority of the sidelink logical channelbelonging to the LCG irrespective of the value of the Destination Indexfield.

In an example, the buffer status reporting procedure may be used toprovide the serving eNB with information about the amount of dataavailable for transmission in the UL buffers associated with the MACentity. RRC controls BSR reporting by configuring timersperiodicBSR-Timer, retxBSR-Timer and logicalChannelSR-ProhibitTimer andby, for a logical channel, optionally signaling logicalChannelGroupwhich allocates the logical channel to an LCG.

In an example, for the buffer status reporting procedure, the MAC entitymay consider radio bearers which are not suspended and may considerradio bearers which are suspended. In an example, a buffer status report(BSR) may be triggered if any of the following events occur: UL data,for a logical channel which belongs to a LCG, becomes available fortransmission in the RLC entity or in the PDCP entity and either the databelongs to a logical channel with higher priority than the priorities ofthe logical channels which belong to any LCG and for which data isalready available for transmission, or there is no data available fortransmission for any of the logical channels which belong to a LCG, inwhich case the BSR may be referred below to as regular BSR; UL resourcesare allocated and number of padding bits is equal to or larger than thesize of the buffer status report MAC control element plus its subheader,in which case the BSR is referred below to as padding BSR; retxBSR-Timerexpires and the MAC entity has data available for transmission for anyof the logical channels which belong to a LCG, in which case the BSR maybe referred below to as regular BSR; periodicBSR-Timer expires, in whichcase the BSR may be referred below to as periodic BSR.

In an example, a MAC entity in a UE, for regular BSR, if the BSR istriggered due to data becoming available for transmission for a logicalchannel for which logicalChannelSR-ProhibitTimer is configured by upperlayers: may start or restart the logicalChannelSR-ProhibitTimer; else:if running, may stop the logicalChannelSR-ProhibitTimer.

In an example, a MAC entity in a UE, for regular and periodic BSR: ifmore than one LCG has data available for transmission in the TTI wherethe BSR is transmitted: may report Long BSR; else may report Short BSR.

In an example, A MAC entity in a UE, for padding BSR: if the number ofpadding bits is equal to or larger than the size of the short BSR plusits subheader but smaller than the size of the long BSR plus itssubheader: if more than one LCG has data available for transmission inthe TTI where the BSR is transmitted: may report truncated BSR of theLCG with the highest priority logical channel with data available fortransmission; else may report Short BSR. Else if the number of paddingbits is equal to or larger than the size of the long BSR plus itssubheader, may report long BSR.

In an example, if the buffer status reporting procedure determines thatat least one BSR has been triggered and not cancelled: if the MAC entityhas UL resources allocated for new transmission for this TTI: instructthe Multiplexing and Assembly procedure to generate the BSR MAC controlelement(s); start or restart periodicBSR-Timer except when the generatedBSRs are Truncated BSRs; start or restart retxBSR-Timer. Else if aRegular BSR has been triggered and logicalChannelSR-ProhibitTimer is notrunning: if an uplink grant is not configured or the Regular BSR was nottriggered due to data becoming available for transmission for a logicalchannel for which logical channel SR masking (logicalChannelSR-Mask) issetup by upper layers: a Scheduling Request may be triggered.

A MAC PDU may contain at most one MAC BSR control element, even whenmultiple events trigger a BSR by the time a BSR can be transmitted inwhich case the regular BSR and the periodic BSR may have precedence overthe padding BSR.

The MAC entity may restart retxBSR-Timer upon indication of a grant fortransmission of new data on any UL-SCH.

Triggered BSRs may be cancelled in case the UL grant(s) in this subframecan accommodate pending data available for transmission but is notsufficient to additionally accommodate the BSR MAC control element plusits subheader. Triggered BSRs may be cancelled when a BSR is included ina MAC PDU for transmission.

The MAC entity may transmit at most one regular/periodic BSR in a TTI.If the MAC entity is requested to transmit multiple MAC PDUs in a TTI,it may include a padding BSR in any of the MAC PDUs which do not containa regular/periodic BSR.

BSRs transmitted in a TTI may reflect the buffer status after MAC PDUshave been built for this TTI. Each LCG may report at the most one bufferstatus value per TTI and this value may be reported in BSRs reportingbuffer status for this LCG. A padding BSR may not be allowed to cancel atriggered regular/periodic BSR. A padding BSR is triggered for aspecific MAC PDU only and the trigger is cancelled when this MAC PDU hasbeen built.

An example scheduling request procedure is described here. TheScheduling Request (SR) may be used for requesting UL-SCH resources fornew transmission. When an SR is triggered, it may be considered aspending until it is cancelled. Pending SR(s) may be cancelled andsr-ProhibitTimer may be stopped when a MAC PDU is assembled and this PDUincludes a BSR which contains buffer status up to (and including) thelast event that triggered a BSR, or, if pending SR(s) are triggered bySidelink BSR, when a MAC PDU is assembled and this PDU includes aSidelink BSR which contains buffer status up to (and including) the lastevent that triggered a Sidelink BSR, or, if pending SR(s) are triggeredby Sidelink BSR, when upper layers configure autonomous resourceselection, or when the UL grant(s) can accommodate pending dataavailable for transmission.

If an SR is triggered and there is no other SR pending, the MAC entitymay set the SR_COUNTER to 0. As long as one SR is pending, the MACentity may for each TTI: if no UL-SCH resources are available for atransmission in this TTI: if the MAC entity has no valid PUCCH resourcefor SR configured in any TTI: may initiate a Random Access procedure onthe SpCell and cancel pending SRs; else if the MAC entity has at leastone valid PUCCH resource for SR configured for this TTI and if this TTIis not part of a measurement gap and if sr-ProhibitTimer is not running:if SR_COUNTER<dsr-TransMax: increment SR_COUNTER by 1; instruct thephysical layer to signal the SR on one valid PUCCH resource for SR;start the sr-ProhibitTimer. Else: notify RRC to release PUCCH forserving cells; notify RRC to release SRS for serving cells; clear anyconfigured downlink assignments and uplink grants; initiate a RandomAccess procedure (see subclause 5.1) on the SpCell and cancel pendingSRs.

The selection of which valid PUCCH resource for SR to signal SR on whenthe MAC entity has more than one valid PUCCH resource for SR in one TTIis left to UE implementation.

FIG. 11 shows an example routing (mapping) restriction according to anexample embodiment.

When routing restrictions for logical channels/bearers are configured,an example embodiment may enhance the BSR process to improve BSR triggerand reporting criteria. In the legacy LTE systems (release 13 andbefore), PDUs could be transmitted on any cell. In the legacy LTEsystems (release 13 and before), when a UE receives an uplink grant onany cell the UE may transmit a TB of any of the logical channelsemploying uplink grant based on logical channel priorities andscheduling mechanisms implemented in the UE. The UE may not starve anyof the logical channels because of the routing restrictions.

When routing restrictions for transmission of logical channels on aplurality of radio resource types are configured, the UE may considerthe routing restrictions into account for transmission of data inlogical channels. In an example, an eNB may need to receive morefrequent BSR reports or BSR reports according to different triggercriteria to properly allocate to wireless devices radio resources ofdifferent types (e.g. LAA cells and/or licensed cells). An eNB may needto know about the BSR of various logical channels to efficientlyallocate uplink grants of different radio resource types. When thesefactors are taken into account, there is a need to improve the BSR MACmechanism to enhance uplink packet transmission and scheduling.

Example embodiments provide enhancements to improve BSR, SR and/or PHRmechanism described above. Example embodiments enable an eNB to receivetimely BSR, SR, and/or PHR and enhance scheduling and/power controlmechanisms in an eNB/UE.

Example embodiments may enhance SR mechanism in an eNB and/or UE, sothat an eNB can efficiently allocate uplink grants in response to an SR.Example embodiments may enhance PHR process, and improve timely deliveryof PHR to an eNB.

Example embodiments enhance uplink packet scheduling and/or powercontrol in an eNB/UE. One or more improvements introduced in examplesembodiments may be combined and implemented together to further increaseefficiency of radio link and MAC mechanisms.

For example, in the current MAC mechanism, the handling of retxBSR-Timermay not provide an efficient mechanism for BSR transmission when routingrestrictions are configured.

In the current release of LTE technology, a Buffer Status Report (BSR)may be triggered if the following event occur: retxBSR-Timer expires andthe MAC entity has data available for transmission for logical channelswhich belong to a LCG, in which case the BSR may be referred below to asRegular BSR. If the buffer status reporting procedure determines that atleast one BSR has been triggered and not cancelled, if the MAC entityhas UL resources allocated for new transmission for this TTI: start orrestart periodicBSR-Timer except when the generated BSRs are TruncatedBSRs; start or restart retxBSR-Timer. The MAC entity may restartretxBSR-Timer upon indication of a grant for transmission of new data onany UL-SCH.

For example, in the current mechanism, the MAC entity may restartretxBSR-Timer upon indication of a grant for transmission of new data onany UL-SCH. In an example, the UE may frequently receive uplink grantson uplink resources of a first radio resource type (e.g. on LAA cells),and may restart retxBSR-Timer. This may prevent BSR to be triggered dueto retxBSR-Timer, while the UE buffer for logical channels that can bemapped on radio resources of a second type (e.g. licensed cells) includedata. The eNB may not receive adequate BSR for logical channels that aremapped to second radio resources type, and may not be able to enhanceuplink scheduling and efficiently transmit efficient uplink grants fortransmission of uplink packets in different logical channels. Exampleembodiments may improve retxBSR-Timer management in a UE.

In an example embodiment, the MAC entity may restart retxBSR-Timer uponindication of a grant for transmission of new data on any UL-SCH via asecond radio resource type (e.g. licensed cell). The MAC entity mayrestart retxBSR-Timer upon indication of a grant for transmission of newdata on any UL-SCH via a first radio resource type (e.g. unlicensedcell) when the configured LCs can be scheduled on the first radioresource type (e.g. unlicensed cell). When one or more logical channelsare configured for transmission only via a second radio resource type(e.g. licensed cell), the MAC entity may not restart retxBSR-Timer uponindication of a grant for transmission of new data on a UL-SCH via thefirst radio resource type (e.g. unlicensed cell). When the configuredLCs can be transmitted on both first and second radio resource types,the MAC entity may restart retxBSR-Timer upon indication of a grant fortransmission of new data on any UL-SCH.

In an example embodiment, the MAC entity may restart retxBSR-Timer uponindication of a grant for transmission of new data on any UL-SCH via asecond radio resource type (e.g. licensed cell). The MAC entity mayrestart retxBSR-Timer upon indication of a grant for transmission of newdata on any UL-SCH on a first radio resource type (e.g. unlicensed cell)when the configured LCs having buffered data can be scheduled on thefirst radio resource type (e.g. unlicensed cell). When one or morelogical channels are configured for transmission only via the secondradio resource type (e.g. licensed cell) and include data in theircorresponding buffer, the MAC entity may not restart retxBSR-Timer uponindication of a grant for transmission of new data on a UL-SCH on viathe first radio resource type (e.g. unlicensed cell). When theconfigured LCs can be transmitted on both radio resource types, the MACentity may restart retxBSR-Timer upon indication of a grant fortransmission of new data on any UL-SCH.

In an example embodiment, the MAC entity may restart retxBSR-Timer uponindication of a grant for transmission of new data on any UL-SCH viasecond radio resource type (e.g. licensed cell). The MAC entity may notrestart retxBSR-Timer upon indication of a grant for transmission of newdata on any UL-SCH via the first radio resource type (e.g. unlicensedcell). This example implementation is simpler to implement, but mayresult in more frequent BSR transmission.

In an example embodiment, two retxBSR-Timers may be configured, one forfirst logical channels mapped to at least one first radio resource typeand one for second logical channels mapped to at least one second radioresource type (e.g. retxBSR-Timer1 and retxBSR-Timer2). For example,retxBSR-Timer1 may be restarted when a grant is received for one of theat least one first radio resource type (e.g. unlicensed cell).retxBSR-Timer2 may restart when a grant is received for one of the atleast one second radio resource type (e.g. licensed cell). In anexample, if any of the timers retxBSR-Timer1 and retxBSR-Timer2 expire,a BSR transmission may be triggered. Timers retxBSR-Timer1 andretxBSR-Timer2 may restart when a BSR is transmitted, wherein the BSRcomprises indication of data comprising data of the at least one firstlogical channel and indication of data comprising data of the at leastone second logical channel. In an example, if the timer retxBSR-Timer1expires, a BSR may be triggered for transmission of a BSR includingindication of amount of data comprising data of at least the at leastone first logical channels. If the timer retxBSR-Timer2 expires, a BSRmay be triggered for transmission of a BSR including indication ofamount of data comprising data of at least the at least one secondlogical channels.

In an example, retxBSR-Timer1 may restart if the BSR includes indicationof amount of data of at least the at least one first logical channelsmapped to the first radio resource type. retxBSR-Timer2 may restart ifthe BSR includes indication of amount of data of at least the at leastone second logical channels mapped to the second radio resource type. Atleast one RRC message configuring one or more cells may comprise a firstvalue for retxBSR-Timer1 and a second value for retxBSR-Timer2. Awireless device may transmit a BSR MAC CE in an uplink grant when a BSRis triggered. A wireless device may trigger and transmit an SR when nouplink grant is available. The eNB may transmit to the wireless devicean uplink grant in response to receiving the SR. The wireless device maytransmit a BSR MAC CE in an uplink grant when a BSR is triggered.

A wireless device may receive one or more messages (e.g. RRC messages)comprising configuration parameters for a plurality of cells and for aplurality of logical channels comprising a first logical channel. Theconfiguration parameters indicate a first mapping restriction of thefirst logical channel to at least one first radio resource types in aplurality of radio resource types. The wireless device receives anuplink grant indicating radio resources of a radio resource type in theplurality of radio resource types. The wireless device restart a firstbuffer status report (BSR) retransmission timer in response to theuplink grant meeting first criteria. The first BSR retransmission timeris employed for triggering a BSR indicating an amount of data comprisingdata of a buffer of the first logical channel. The first criteriacomprise the radio resource type being of one of the at least one firstradio resource type. The wireless device may restart the first BSRretransmission timer in response to transmitting a BSR that comprises areport for a buffer of a first logical channel that triggered the BSR.In an example, the wireless device may not restart a first buffer statusreport (BSR) retransmission timer in response to transmitting a BSR,when the BSR does not comprise a report for a buffer of a first logicalchannel that triggered the BSR.

The wireless device may restart a second BSR retransmission timer inresponse to the uplink grant meeting second criteria. The second BSRretransmission timer is employed for triggering a BSR indicating anamount of data comprising data of a buffer of a second logical channel.The second criteria may comprise the radio resource type being of atleast one second radio resource type.

The wireless device may trigger a BSR transmission in response to thefirst BSR retransmission timer expiring. The wireless device may receivean uplink grant from the base station. The wireless device may transmita transport block comprising a BSR to the base station.

In an example, the radio resource type indicates a cell type. The celltype comprises at least one of the following: a licensed cell type andan unlicensed cell type. The mapping restriction may be based, at leastin part, on one or more quality of service (QoS) requirements of thelogical channel. A QoS requirement is based on a latency requirement ofthe logical channel. The logical channel is configured with a priorityand a prioritized bit rate (PBR). The at least one message comprises aparameter indicating a value for the first BSR retransmission timer.

For example, in the current MAC mechanism, the handling of retxBSR-Timermay not provide an efficient mechanism for BSR transmission when routingrestrictions are configured. In the current LTE implementation, a bufferstatus report (BSR) may be triggered if any of the following eventsoccur: retxBSR-Timer expires and the MAC entity has data available fortransmission for any of the logical channels which belong to a LCG, inwhich case the BSR may be referred below to as regular BSR. If thebuffer status reporting procedure determines that at least one BSR hasbeen triggered and not cancelled, if the MAC entity has UL resourcesallocated for new transmission for this TTI: start or restartperiodicBSR-Timer except when the generated BSRs are truncated BSRs;start or restart retxBSR-Timer. The MAC entity may restart retxBSR-Timerupon indication of a grant for transmission of new data on any UL-SCH.

For example, in the current mechanism, the MAC entity may restartretxBSR-Timer upon transmission of a truncated BSR. In an example, thetruncated BSR may include the BSR for the logical channel group with thehighest priority. In an example, the truncated BSR may include BSR ofthe buffers that are mapped only to a second radio resource type. In anexample, the truncated BSR may not include BSR of the buffers that aremapped to both a first radio resource type and a second radio resourcetype. Such a BSR may not provide enough information to eNB forscheduling. The eNB may then schedule resources on the second radioresource type, since it may not receive adequate information aboutlogical channels that could be transmitted on the first radio resourcetype. In an example embodiment, BSR mechanism may be improved to enhanceBSR transmission so that an eNB receives adequate BSR reports fromlogical channels in example scenarios.

In an example embodiment, the start or restart retxBSR-Timer process maybe enhanced. In an example embodiment, if the buffer status reportingprocedure determines that at least one BSR has been triggered and notcancelled, if the MAC entity has UL resources allocated for newtransmission for this TTI, the UE may start or restart retxBSR-Timercorresponding to a logical channel (or LGC) when the BSR includes anindication of the data of the logical channel (or LGC). For example, theUE may not start or restart retxBSR-Timer when the generated BSRs areTruncated BSRs. In legacy mechanism, periodicBSR-Timer and retxBSR-Timerare treated differently. In an example embodiment, additionalrestriction is added to further limit the start or restart ofretxBSR-Timer.

In an example embodiment, if the buffer status reporting proceduredetermines that at least one BSR has been triggered and not cancelled,if the MAC entity has UL resources allocated for new transmission forthis TTI, the UE may start or restart retxBSR-Timer except: when thegenerated BSRs are Truncated BSRs and UE has available data for a LCtype and BSR for that logical channel type is not reported in thetruncated BSR.

In an example embodiment, if the buffer status reporting proceduredetermines that at least one BSR has been triggered and not cancelled,if the MAC entity has UL resources allocated for new transmission forthis TTI, the UE may start or restart retxBSR-Timer except: when thegenerated BSRs are Truncated BSRs and UE is configured with logicalchannels that can only be transmitted on the second radio resource type.

In an example embodiment, if the Buffer Status reporting proceduredetermines that at least one BSR has been triggered and not cancelled,if the MAC entity has UL resources allocated for new transmission forthis TTI, the UE may start or restart retxBSR-Timer except: when thegenerated BSRs are Truncated BSRs and UE is configured with at least twotypes of logical channels with different routing restrictions. Othersimilar examples may be provided to introduce additional exceptions forstart or restarting retxBSR-Timer when a truncated BSR is reported.

In the current LTE-A MAC specifications, a Buffer Status Report (BSR)may be triggered if any of the following events occur: UL data, for alogical channel which belongs to a LCG, becomes available fortransmission in the RLC entity or in the PDCP entity and either the databelongs to a logical channel with higher priority than the priorities ofthe logical channels which belong to any LCG and for which data isalready available for transmission, or there is no data available fortransmission for any of the logical channels which belong to a LCG, inwhich case the BSR may be referred below to as Regular BSR; UL resourcesare allocated and number of padding bits is equal to or larger than thesize of the Buffer Status Report MAC control element plus its subheader,in which case the BSR is referred below to as Padding BSR; retxBSR-Timerexpires and the MAC entity has data available for transmission for anyof the logical channels which belong to a LCG, in which case the BSR maybe referred below to as Regular BSR; periodicBSR-Timer expires, in whichcase the BSR may be referred below to as Periodic BSR.

The existing mechanism does not consider routing restrictions forlogical channels. There is a need to trigger BSR depending when UL databecomes available on a logical channel and depending on routingrestriction configuration of the logical channel and other logicalchannel which data is already available for transmission. Examplemechanisms improve BSR trigger mechanism to provide adequate BSRinformation to the eNB. This mechanism may enhance uplink scheduling inan eNB.

In the current MAC algorithm, regular BSR is triggered when: UL data,for a logical channel which belongs to a LCG, becomes available fortransmission and either the data belongs to a logical channel withhigher priority than the priorities of the logical channels which belongto any LCG and for which data is already available for transmission, orthere is no data available for transmission for any of the logicalchannels which belong to a LCG.

In an example embodiment, regular BSR is triggered when: UL data, for alogical channel which belongs to a LCG, becomes available fortransmission and either the data belongs to a logical channel that canbe transmitted on first and second radio resource types and the logicalchannels which belong to any LCG and for which data is already availablefor transmission can be only transmitted on the second radio resourcetype, or the data belongs to a logical channel that can only betransmitted on the second radio resource type and the logical channelswhich belong to any LCG and for which data is already available fortransmission can be transmitted on the first and second radio resourcetype, or there is no data available for transmission for any of thelogical channels which belong to a LCG.

In an example embodiment, enhanced mechanisms may be combined withlegacy mechanisms. The example embodiments may trigger a BSR when databecomes available for a logical channel with a first routing restrictionthat is different from the routing restriction of other logical channelswith data. This process may be combined with logical channel priorities.

In an example embodiment, regular BSR is triggered when: for logicalchannels with a first routing restriction (e.g. transmission only onlicensed cells): UL data, for a logical channel which belongs to a LCG,becomes available for transmission and either the data belongs to alogical channel with higher priority than the priorities of the logicalchannels which belong to any LCG and for which data is already availablefor transmission, or there is no data available for transmission for anyof the logical channels which belong to a LCG. Regular BSR is triggeredwhen: for logical channels with a second routing restriction (e.g.transmission on licensed/LAA cells): UL data, for a logical channelwhich belongs to a LCG, becomes available for transmission and eitherthe data belongs to a logical channel with higher priority than thepriorities of the logical channels which belong to any LCG and for whichdata is already available for transmission, or there is no dataavailable for transmission for any of the logical channels which belongto a LCG.

In an example embodiment, regular BSR is triggered when: UL data, for alogical channel which belongs to a LCG, becomes available fortransmission on a logical channel with a first routing restriction andeither the data belongs to a logical channel with a different routingrestriction than the routing restriction of the logical channels whichbelong to any LCG and for which data is already available fortransmission, or there is no data available for transmission for any ofthe logical channels which belong to a LCG.

The wireless device receives one or more messages comprisingconfiguration parameters for a plurality of cells and a plurality oflogical channels comprising a logical channel. The configurationparameters indicate a mapping restriction of the logical channel to oneor more radio resource types in a plurality of radio resource types. Thewireless device triggers a buffer status report (BSR) transmission whendata becomes available for the logical channel with the mappingrestriction and when a selected set of one or more logical channels withthe same mapping restriction meet a first criteria. In an example, thefirst criteria comprise: the selected set of one or more logicalchannels with the same mapping restriction do not include uplink bufferdata. In an example, the first criteria comprise: the selected set ofone or more logical channels with the same mapping restriction do notinclude uplink buffer data; the logical channel has a higher prioritythan the selected set of one or more logical channels.

In an example, buffers of logical channels that have the same mappingrestriction (e.g. mapped to the same one or more radio resource types)are considered for determining whether a BSR is triggered. In an exampleone or more first logical channels are mapped to one or more first radioresource type and one or more second logical channels are mapped to oneor more second radio resource type.

For example, a first buffer status report is triggered based onavailability of data in at least one of one or more first logicalchannels, and independent of availability of data in the one or moresecond logical channels. The condition for triggering a first BSR maydepends on availability of new data on a first logical channel with amapping restriction and may also depend of availability of existing datain other logical channels with the same mapping restriction.

A second buffer status report may be triggered based on availability ofdata in at least one of one or more second logical channels, andindependent of availability of data in the one or more first logicalchannels. The condition for triggering a first BSR may depends onavailability of new data on a second logical channel a mappingrestriction and may also depend of availability of existing data inother logical channels with the same mapping restriction.

The wireless device receives an uplink grant indicating radio resourcesof a first radio resource type. The wireless device constructs atransport block comprising the BSR. The wireless device transmits thetransport block via the radio resources of the first radio resourcetype.

In an example, the radio resource type indicates a cell type. The celltype comprises at least one of the following: a licensed cell type andan unlicensed cell type. The mapping restriction is based, at least inpart, on one or more quality of service (QoS) requirements of thelogical channel. A QoS requirement is based on a latency requirement ofthe logical channel. The logical channel is configured with a priorityand a prioritized bit rate (PBR).

In the current SR process, when an SR is triggered, it may be consideredas pending until it is cancelled. Pending SR(s) may be cancelled andsr-ProhibitTimer may be stopped when a MAC PDU is assembled and this PDUincludes a BSR which contains buffer status up to (and including) thelast event that triggered a BSR, or when the UL grant(s) can accommodatepending data available for transmission.

When an eNB receives an SR signal from a UE, the eNB provides an uplinkgrant to the UE. In the current LTE mechanism, there is no restrictionon routing restriction of logical channels on different cells, and theeNB may grant uplink grant on any of the configured and activated cells.

When routing restrictions are configured, data buffered in some of thelogical channels may not be configured for transmission on a first radioresource type.

In an example embodiment, an eNB scheduling mechanism may be enhanced inresponse to a received SR. The example embodiment may enhance eNBscheduling mechanism and may reduce uplink packet transmission delaywhen an SR is triggered.

In an example embodiment, if an SR is triggered and the eNB receives anSR from a UE and when eNB/UE configures at least one LC that can only betransmitted on a second radio resource type, then eNB grants ULresources on the second radio resource type in response to SR. In anexample embodiment, the eNB may employ LC/bearer configuration indetermining to transmit uplink grants on a first radio resource type ora second radio resource type. For example, when eNB/UE is configuredwith one or more LCs that can only be transmitted on the second radioresource type, the eNB may grant uplink resources on the second radioresource type in response to an SR. For example, when eNB/UE isconfigured with one or more LCs that can be transmitted on both thefirst and second radio resource type, the eNB may grant uplink resourceson either the first radio resource type and/or the second radio resourcetype in response to an SR.

In an example implementation, when a UE triggers/transmits SR inresponse to data on a buffer of a LC that can only be transmitted on thesecond radio resource type, the UE may not cancel SR process and maymaintain the SR process pending, when the UE receives a grant on thefirst radio resource type.

In an example implementation, when a UE triggers/transmits SR inresponse to data on a buffer of a LC that can only be transmitted on asecond radio resource type, the UE may transmit BSR in the uplink grantand cancel SR, when the UE receives grant on the first radio resourcetype and/or the second radio resource type.

In an example embodiment, the Buffer Status Reporting may be importantfor UL scheduling, and contains the buffer status for the signalingmessages e.g. measurement report (which is related to the handover)and/or data. The loss of the BSR may impact UE performance. The PowerHeadroom Reporting may provide the serving eNB with information aboutthe difference between the nominal UE maximum transmit power and theestimated power for UL-SCH transmission per activated Serving Cell,which is also essential for UL scheduling. In an example embodiment, theBSR and PHR MAC CE may be configured to be sent only over the secondradio resource type.

The following example routing restrictions for MAC CEs alternatives maybe considered: A MAC CE is sent on the first radio resource type when nogrant is received for the second radio resource type. In an example, ifMAC CEs are sent on the first radio resource type they may be delayedmore than they would be if they were sent on the second radio resourcetype. In an example, when grants are received on both first and secondradio resource types, the UE may transmit the MAC CE on the second radioresource type.

In an example, the UE may not consider a MAC CE transmitted until the UEhas received an ACK for it, hence the UE may resend this MAC CE onanother radio resource type (e.g. licensed cell). While this wouldresult in the shortest delay, it may complicate MAC BSR and PHR timermanagements. When the UE gets two grants; one on the first radioresource type an one on the second radio resource type then the UE maysend the MAC CEs on the second radio resource type. This exampleimplementation may enable that the UE is not blocking MAC CEs from beingtransmitted on the first radio resource type, further it enables that ifthe UE gets scheduled on both first and second radio resource types thenthe UE may prioritize to send MAC CEs on the second radio resource type.In an example embodiment, MAC CEs may be sent on first or second radioresource types. In an example, if the UE has valid grants both for firstand second radio resource types, the UE may send MAC CEs on the secondradio resource type.

In an example embodiment, an eNB may transmit one or more RRC messagesto configure routing restriction for transmission of MAC CEs in theuplink. In an example embodiment, routing restriction for transmissionof MAC CEs in the uplink may be preconfigured (pre-specified in theUE/eNB). For example, the UE may transmit one or more MAC CEs only on asecond radio resource type.

When BSR can only be transmitted on a specific radio resource type, BSRmechanisms may need to be enhanced to ensure that the eNB receivesadequate BSR and is enabled to provide efficient uplink scheduling toUEs.

In an example embodiment, if the Buffer Status reporting proceduredetermines that at least one BSR has been triggered and not cancelled:if the MAC entity has UL resources allocated for new transmission on atleast one second radio resource type for this TTI, the MAC entity may:instruct the Multiplexing and Assembly procedure to generate the BSR MACcontrol element(s); start or restart periodicBSR-Timer except when thegenerated BSRs are Truncated BSRs; and/or start or restartretxBSR-Timer; else if a Regular BSR has been triggered andlogicalChannelSR-ProhibitTimer is not running: if an uplink grant is notconfigured or the Regular BSR was not triggered due to data becomingavailable for transmission for a logical channel for which logicalchannel SR masking (logicalChannelSR-Mask) is setup by upper layers: theUE may trigger a Scheduling Request. In an example embodiment, when BSRare triggered and UE does not have a grant on a second radio resourcetype, the UE may trigger a Scheduling Request (if the Scheduling Requestis configured, e.g. not masked, for the logical channel triggering theBSR).

In an example embodiment, when BSR is triggered due to traffic onlogical channels routable to both first and second radio resource types(or when UE has data only on logical channels routable to both first andsecond radio resource types), the UE may not trigger SR for transmissionof BSR when the UE receives uplink grants on the first radio resourcetype. The UE may transmit a MAC PDU on the first radio resource type inresponse to the uplink grant.

In an example embodiment, when PHR is triggered and UE does not have agrant on a second radio resource type, the UE may trigger a SchedulingRequest. A UE may not be configured to transmit the PHR on a first radioresource type. The UE may trigger an SR for transmission of PHR. The UEmay receive uplink grants and transmit PHR in response to the uplinkgrant. In an example embodiment, the UE may cancel the SR when the grantis received on the second radio resource type, otherwise the UE maymaintain the SR process pending.

In an example embodiment, when PHR is triggered and UE does not have agrant on a second radio resource type, the UE may trigger a SchedulingRequest when the UE receives grants on the first radio resource type.PHR may have useful information for the eNB uplink scheduling and powercontrol. SR may not be triggered for PHR if UE does not receive anyuplink grants. A UE may not be configured to transmit the PHR on thefirst radio resource type. The UE may trigger an SR for transmission ofPHR when it receives uplink grants on the first radio resource type. TheUE may receive uplink grants on a second radio resource type andtransmit PHR in response to the uplink grant. In an example embodiment,the UE may cancel the SR when the grant is received on a second radioresource type, otherwise the UE may maintain the SR process pending.

In an example embodiment, a wireless device may receive one or moremessages (e.g. RRC messages) comprising configuration parameters for aplurality of cells and for a plurality of logical channels. Theconfiguration parameters may indicate a mapping restriction of a logicalchannel to one or more radio resource types in a plurality of radioresource types. When a logical channel is mapped to one or more radioresource types, data in the buffer of the logical channel can only betransmitted via the one or more radio resource types.

In an example, the wireless device may trigger a first schedulingrequest (SR) process for uplink transmissions requiring uplink resourcesof at least one first radio resource type. For example, uplinktransmissions may be for data in a logical channel mapped to the atleast one first radio resource type. For example, uplink transmissionsmay be for a MAC CE and/or a control message/signaling that requiresresources of at least one first radio resource type. The uplinktransmissions may comprise one or more transport blocks. The uplinktransmissions may comprise one or more media access control (MAC)control elements. The one or more messages indicate a first mappingrestriction of the uplink transmissions to uplink resources of the atleast one first radio resource type.

In an example, the wireless device, in response to triggering the firstscheduling request (SR) process, may transmit to the base station afirst SR signal on an uplink control channel and the wireless device maystart a first scheduling request prohibit timer. The first SR signal mayindicate that the wireless device requires radio resources of at leastone first radio resource type. In an example, the base station maydetermine that the first SR signal is for a request for the at least onefirst radio resource type based on the at least one message (RRCsignaling) transmitted to the wireless device. In an example, the one ormore messages indicate that the uplink transmissions require uplinkresources of the at least one first radio resource type.

The at least one message may comprise configuration parameters ofscheduling resources in an uplink physical control channel. The wirelessdevice receives from a base station an uplink grant indicating uplinkradio resources. An uplink grant may be received via the base stationtransmitting a DCI on the downlink physical control channel. The DCI maycomprise the uplink grant indicating uplink resource blocks,transmission format and scheduling information and/or radio resourcetype for an uplink transmission.

In an example embodiment, the wireless device may cancel the first SRprocess if the uplink radio resources are of the one of the at least onefirst radio resource type. Otherwise, the wireless device may maintainthe first SR process pending. The wireless device transmits one or moretransport blocks via the uplink radio resources. The wireless device maymonitor at least one downlink control channel for subsequent uplinkgrants. The wireless device may cancel the SR process when the wirelessdevice transmits the uplink transmissions (that triggered the first SRprocess) employing an uplink grant. In an example, the wireless devicemay cancel the first SR process when the wireless device transmits a BSRthat comprises information about an amount of data in a logical channelthat triggered the first SR process.

In an example, the one or more transport blocks comprises the uplinktransmissions if the uplink radio resources are of one of the at leastone first radio resource type. In an example, the radio resource typemay indicate a cell type. In an example, the cell type comprises atleast one of the following: a licensed cell type and an unlicensed celltype.

Example power headroom trigger condition configuration parameters in anRRC message are shown below. Other examples may be implemented.phr-Config CHOICE {release NULL, setup SEQUENCE {periodicPHR-TimerENUMERATED {sf10, sf20, sf50, sf100, sf200, sf500, sf1000, infinity},prohibitPHR-Timer ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200,sf500, sf1000}, dl-PathlossChange ENUMERATED {dB1, dB3, dB6, infinity}}

The parameter periodicPHR-Timer may be a timer for PHR reporting. Valuein number of sub-frames. Value sf10 corresponds to 10 subframes, sf20corresponds to 20 subframes and so on.

The parameter prohibitPHR-Timer may be a timer for PHR reporting. Valuein number of sub-frames. Value sf0 corresponds to 0 subframes, sf100corresponds to 100 subframes and so on.

The parameter dl-PathlossChange may be DL Pathloss Change and the changeof the required power backoff due to power management (as allowed byP-MPRc) for PHR reporting. Value in dB. Value dB1 corresponds to 1 dB,dB3 corresponds to 3 dB and so on. The same value may apply for eachserving cell (although the associated functionality is performedindependently for each cell).

A Power Headroom reporting procedure may be employed to provide aserving eNB with information about the difference between nominal UEmaximum transmit power and estimated power for UL-SCH transmission peractivated serving cell. The Power Headroom reporting procedure may alsoto provide a serving eNB with information about the difference betweenthe nominal UE maximum power and the estimated power for an UL-SCH andPUCCH transmission on a SpCell and/or a PUCCH SCell.

The reporting period, delay and mapping of Power Headroom may bedefined. An RRC may control Power Headroom reporting by configuring atleast two timers periodicPHR-Timer and prohibitPHR-Timer, and bysignaling dl-PathlossChange which may set the change in measureddownlink pathloss and the power backoff due to power management (asallowed by P-MPRc) to trigger a PHR.

In an example embodiment, a Power Headroom Report (PHR) may be triggeredif one or more of the following events occur (not listed in anyparticular order). First, a prohibitPHR-Timer expires or has expired andthe path loss has changed more than dl-PathlossChange dB for at leastone activated serving cell of any MAC entity which is used as a pathlossreference since the last transmission of a PHR in this MAC entity whenthe MAC entity has UL resources for new transmission. Second, aperiodicPHR-Timer expires. Third, upon configuration or reconfigurationof the power headroom reporting functionality by upper layers, which isnot used to disable the function. Fourth, activation of an SCell of anyMAC entity with a configured uplink; Fifth, addition of an PSCell;and/or sixth, a prohibitPHR-Timer expires or has expired, when the MACentity has UL resources for a new transmission, and the following istrue in this TTI for any of the activated serving cells of any MACentity with a configured uplink (there may be UL resources allocated fortransmission or there may be a PUCCH transmission on this cell, and therequired power backoff due to power management (as allowed by P-MPRc)for this cell has changed more than dl-PathlossChange dB since the lasttransmission of a PHR when the MAC entity had UL resources allocated fortransmission or PUCCH transmission on this cell).

In an example implementation, the MAC entity may avoid triggering a PHRwhen the required power backoff due to power management decreasestemporarily (e.g. for up to a few tens of milliseconds) and it may avoidreflecting such temporary decrease in the values of PCMAX,c/PH when aPHR is triggered by other triggering conditions.

If the MAC entity has UL resources allocated for a new transmission forthis TTI, the MAC entity may start a periodicPHR-Timer if it is thefirst UL resource allocated for a new transmission since the last MACreset. A UE may transmit a corresponding PHR report if a Power Headroomreporting procedure determines that at least one PHR has been triggeredand not cancelled, and if the allocated UL resources can accommodate acorresponding PHR MAC control element plus its subheader for acorresponding PHR configuration as a result of logical channelprioritization.

For example, a UE may transmit a corresponding PHR report for one ormore activated serving cells with a configured uplink if: the allocatedUL resources can accommodate a PHR MAC control element plus itssubheader if neither extendedPHR nor dualConnectivityPHR is configured,and/or an Extended PHR MAC control element plus its subheader if anextendedPHR is configured, and/or a Dual Connectivity PHR MAC controlelement plus its subheader if dualConnectivityPHR is configured as aresult of logical channel prioritization.

In LTE Release-10 carrier aggregation (CA), an Extended Power HeadroomReport (PHR) MAC Control Element (CE) was introduced to accommodate type2 power headroom (PH) of PCell and type 1 PHs of SCells. Type 2 PH maybe employed when simultaneousPUCCH-PUSCH configuration is supported. InDC, since a PUCCH may be transmitted on a PCell and an PSCell, the PHRMAC CE may contain 2 type 2 PHs and several type 1 PHs. DC PHR MAC CEwas introduced to include an extra type 2 PH of a PSCell. For DC, PH maybe reported to both eNBs separately, but the PHR may include PH foractive serving cells.

In LTE Release-12, three types of power headroom related MAC CEs aredefined: 1) a Power Headroom Report MAC CE, 2) An Extended PowerHeadroom Report MAC CE, and 3) Dual Connectivity Power Headroom. A MACCE may be identified by a logical channel ID (LCID) field in a MACsubheader. The LCID field may identify the logical channel instance ofthe corresponding MAC SDU and/or the type of the corresponding MACcontrol element and/or padding.

Values of LCID for UL-SCH MAC CE in Release-12 are defined in 3GPP TS36.321 V12.4.0 as: Index 11000: Dual Connectivity Power Headroom Report;Index 11001: Extended Power Headroom Report; and Index 11010: PowerHeadroom Report

If an extendedPHR mode is configured and when conditions fortransmission of a PHR are met, a UE may generate and transmit anExtended PHR MAC control element identified by, for example, LCID=11001.

If a dualConnectivityPHR mode is configured and when conditions fortransmission of a PHR are met, a UE may generate and transmit a DualConnectivity Power Headroom Report identified by, for example,LCID=11000.

If a PHR is configured but neither extendedPHR mode nordualConnectivityPHR mode is configured, and when conditions fortransmission of a PHR are met, then a UE may generate and transmit aPower Headroom Report with, for example, an LCID of 11010.

LTE Release-12 does not appear to address configuration, message format,trigger conditions, and message processing for power headroom when aPUCCH SCell with simultaneous PUCCH+PUSCH transmissions is configured ina UE (without configuring DC in the UE). A Release-12 Dual ConnectivityPower Headroom Report may not be applicable in such a scenario, sincedual connectivity may not be configured in the UE. A Release-12 ExtendedPower Headroom Report may not be applicable since it does not appear tosupport transmission of two Type 2 power headrooms when PUCCH groups areconfigured. A Release-12 Power Headroom Report report may not beapplicable since it appears to support only one serving cell. There maybe a need for enhancing the power headroom implementation to efficientlysupport PUCCH group configuration. There may also be a need forenhancing the power headroom implementation to enhanced cellconfigurations not supported by existing PHR formats.

A new PHR may be called an extendedPHR2 MAC CE and/or an extended cellconfiguration PHR MAC CE and/or a new extended PHR MAC CE. The new PHRmay also be called by other names (e.g. PUCCH group PHR MAC CE, enhancedconfiguration MAC CE, 32 cell PHR MAC CE, etc., and/or the like). AnExtendedPHR2 MAC CE may also support additional features in addition toPUCCH groups. For example, an ExtendedPHR2 MAC CE may support more than5 cells including a primary cell and more than k secondary cells (e.g.k=4, 7, etc., may support up to 32 cells) and/or many other features.

The number of used MAC LCIDs may increase if a new PHR MAC CE commandformat with a new MAC LCID is implemented for an extendedPHR2. A MACLCID may be included in a MAC subheader. In an example embodiment, anexisting MAC LCID may be employed for an extendedPHR2 (e.g. LCID ofExtended PHR). A UE may transmit PHR MAC CEs to an eNB in unicastmessages. Both the UE and the eNB may have information about the currentRRC configurations of the UE. The UE may use the same LCID for or one ormore PHR transmissions and the UE may identify the format of the PHRbased on RRC configuration parameters.

This enhancement may not require introducing a new LCID for anextendedPHR2. Two different power headroom MAC CEs may use the sameLCID. This mechanism may reduce the number of LCIDs used in the MAClayer (compared with the scenario wherein a new LCID is introduced) andmay further simplify a UE implementation. RRC configuration parametersin addition to an LCID may be employed to determine the format of thePHR MAC CE.

A UE may consider UE RRC cell configurations to decide the format of aPHR MAC CE. For example, if a UE is configured with a first RRCconfiguration for a plurality of cells (e.g. 5 cells) of an eNB with noconfigured PUCCH SCell, then the fields in the MAC CE may be updatedusing processes related to an extendedPHR power headroom. If a UE isconfigured with PUCCH groups, then the fields in the MAC CE may beupdated using processes related to an extendedPHR2 PHR. On the otherhand, an eNB receiving the PHR MAC CE may have information about the RRCconfiguration of the UE transmitting the PHR MAC CE, and may interpretthe PHR MAC CE fields based on the corresponding RRC configuration.

An eNB may transmit one or more RRC configuration parameters comprisingconfiguration parameters of one or more cells. The configurationparameters for a cell may comprise configuration parameters for powerheadroom. The UE may use RRC configuration parameters to determine whichtype of the PHR headroom the UE should transmit.

In an example embodiment, a UE may transmit its capability regardingsupporting simultaneousPUCCH-PUSCH to the eNB in an RRC UE CapabilityIE. For example: simultaneousPUCCH-PUSCH-r10 ENUMERATED {supported}OPTIONAL. The eNB may then configure simultaneousPUCCH-PUSCH for PCelland/or PUCCH SCell using information elements in RRC control messages.For example: simultaneousPUCCH-PUSCH ENUMERATED {true} OPTIONAL, NeedOR. simultaneousPUCCH-PUSCH IE may indicate whether simultaneous PUCCHand PUSCH transmissions is configured in a PUCCH group. In an example,E-UTRAN may configure this field, when thenonContiguousUL-RA-WithinCC-Info is set to supported in the band onwhich PCell (or e.g. PUCCH SCell) is configured.

In LTE-A release 12 and before, Type 2 power headroom is reported whensimultaneousPUCCH-PUSCH is configured for a given cell, for examplePCell or PSCell. PCell and PSCell are always active after they areconfigured. When simultaneousPUCCH-PUSCH is configured, Type 1 and Type2 PH fields for PCell and PSCell are included in the PHR report.simultaneousPUCCH-PUSCH may be configured for PUCCH SCell. In Release 12and before, the presence of Type2 PH depends on thesimultaneousPUCCH-PUSCH configuration. If a UE is not configured withsimultaneousPUCCH-PUSCH, the UE transmits UCI on PUSCH and the paralleltransmission of PUCCH and PUSCH does not occur. In this case, the UEdoes not transmit Type2 PH in the PHR report. When a UE is configuredwith simultaneousPUCCH-PUSCH, the UE may transmit UCI on PUCCH whenPUSCH resource is allocated. In this case, the UE transmits Type2 PH inthe PHR report.

In 3GPP RAN2 meeting number 91 in September 2015, it was agreed thatpresence of Type 2 PH for both PCell and PUCCH SCell follows theconfiguration of simultaneousPUCCH-PUSCH of the corresponding PUCCH. IfsimultaneousPUCCH-PUSCH is not configured for a PUCCH group, then Type 2PH is not reported for that group. This mechanism may createinefficiencies and/or issues when multiple PUCCH groups are configured.This mechanism may not provide adequate transmit power information tothe eNB for an efficient uplink scheduling and power control. Whenmultiple PUCCH groups are configured and when simultaneousPUCCH-PUSCH isnot configured for a cell group, parallel transmission of PUSCH and UCImay still be possible. In an example embodiment, UCI in one PUCCH groupmay be transmitted in parallel with PUSCH in another PUCCH group. Thereis a need to improve mechanisms for transmission of Type 2 PHR for thePCell and PUCCH SCell based on RRC configuration parameters when PUCCHgroups are configured.

When PUCCH groups are configured, UCI multiplexing on PUSCH is on perPUCCH group basis. The simultaneous transmission of PUCCH and PUSCH mayoccur when UE is configured with PUCCH SCell and simultaneousPUCCH-PUSCHis not configured.

In an example embodiment, when PUCCH groups are configured, UCI on PUSCHis performed per PUCCH group. A UE may multiplex UCIs of a primary PUCCHgroup on the PUSCH of a serving cell in primary PUCCH group. A UE maynot multiplex UCIs of primary PUCCH group on PUSCH of a serving cell insecondary PUCCH group. A UE may multiplex UCIs of a secondary PUCCHgroup on the PUSCH of a serving cell in the secondary PUCCH group. A UEmay not multiplex UCIs of a secondary PUCCH group on PUSCH of a servingcell in another PUCCH group, e.g. the primary PUCCH group.

When PUCCH groups are configured, the configuration ofsimultaneousPUCCH-PUSCH may be configured independently on PCell orPUCCH SCell. For example, the parameter simultaneousPUCCH-PUSCH may beconfigured on both PCell and PUCCH SCell (set as true). For example,simultaneousPUCCH-PUSCH may be configured for one of PCell or PUCCHSCell. Or in another example, simultaneousPUCCH-PUSCH may not beconfigured on either PCell or PUCCH SCell.

In an example embodiment, independent of whether simultaneousPUCCH-PUSCHis configured (set to true) or not, UCI in one cell group may betransmitted in PUCCH of one cell group, in parallel with PUSCHtransmission in another cell group. Even when simultaneousPUCCH-PUSCH isconfigured for neither PCell nor PUCCH SCell, parallel transmission ofPUCCH and PUSCH is still possible. If UE is configured with PUCCH SCell,simultaneous transmission of PUCCH and PUSCH may occur independent ofthe configuration of simultaneousPUCCH-PUSCH on either PCell or PUCCHSCell.

According to the current agreement, a PHR may be reported without anyType 2 PH even if PUCCH can be transmitted in the same subframe asPUSCH. Such PHR transmission mechanism may not provide adequate powerheadroom information to eNB for an efficient uplink power control. Inrelease 13 carrier aggregation, PUCCH groups may be configured under oneMAC entity. A UE may transmit multiple PUCCHs to the same eNB.

In an example solution to this problem, a mechanism may be implementedin which Type 2 PH is reported for PCell when PUCCH on SCell isconfigured, regardless of configuration of simultaneousPUCCH-PUSCH oneither PCell or PUCCH SCell. Such mechanism may result in additionalinefficiencies. The mechanism may transmit Type 2 PHR for a PCell whenit is not needed by the eNB. A PUCCH SCell may be deactivated and inthat case the above mechanism may transmit unnecessary PCell Type 2power headroom (e.g. even if simultaneousPUCCH-PUSCH is not configuredfor the PCell). Such solution may provide unneeded PCell Type 2 PHR tothe eNB in some scenarios.

In an example solution, Type 2 PH may be reported for PUCCH SCell whenPUCCH on SCell is configured, regardless of configuration ofsimultaneousPUCCH-PUSCH on either PCell or PUCCH SCell. Such mechanismmay transmit Type 2 PHR for an SCell when it is not needed by the eNB,for example when PUCCH SCell is deactivated. This mechanism may resultin additional signaling overhead and computation on the UE. A moreeffective mechanism may be needed to enhance PHR report process andmechanism in a UE and an eNB.

Examples in the above two paragraphs are examples of inefficientsolutions. There is a need to further improve PHR process. An exampleembodiment, enhance PHR transmission mechanisms, e.g., when multiplePUCCH SCells are configured.

In an example embodiment, Type 1 and Type 2 PH may not be transmittedfor a deactivated PUCCH SCell when PUCCH on SCell is configured. Type 2PH is transmitted for an activated PUCCH SCell regardless of whethersimultaneousPUCCH-PUSCH is configured for the PUCCH SCell or not.

In an example embodiment, a PUCCH SCell may be deactivated in somescenarios. If and when PUCCH SCell is deactivated, there is no need toinclude Type 1 and Type 2 PH reports in the PHR for the PUCCH SCell.This requires implementation of new processes and format of PHR, inwhich Type 2 and/or Type 1 PHR may or may not be reported for a PUCCHSCell.

In an example embodiment, a PUCCH SCell may be deactivated in somescenarios. Transmission of Type 2 PH for a PCell may depend on whetherPUCCH SCell is activated or deactivated. When a PUCCH SCell isconfigured and activated, Type 2 PH is transmitted for the PCell and thePUCCH SCell regardless of whether simultaneousPUCCH-PUSCH is configuredor not configured for the PCell and/or the PUCCH SCell. When the PUCCHSCell is activated, UCI on PUCCH may be transmitted in parallel withPUSCH regardless of whether simultaneousPUCCH-PUSCH is configured forthe PCell or not.

When a PUCCH SCell is configured and deactivated, a Type 2 PH istransmitted for the PCell only when simultaneousPUCCH-PUSCH isconfigured for the PCell. When PUCCH SCell is deactivated, UCI on PUCCHof PCell may not be transmitted in parallel with PUSCH whensimultaneousPUCCH-PUSCH is not configured. When PUCCH SCell isdeactivated, UCI on PUCCH may be transmitted in parallel with PUSCH whensimultaneousPUCCH-PUSCH is configured.

In an example embodiment, when extendedPHR2 PHR is reported, themechanism for reporting Type 2 PH may be according to the followingprocess: if a PUCCH SCell is configured and activated: (regardless ofconfiguration of simultaneousPUCCH-PUSCH); obtain the value of the Type2 power headroom for the PCell; obtain the value for the correspondingPCMAX,c field from the physical layer; obtain the value of the Type 2power headroom for the PUCCH SCell; obtain the value for thecorresponding PCMAX,c field from the physical layer; else ifsimultaneousPUCCH-PUSCH is configured for PCell: obtain the value of theType 2 power headroom for the PCell; obtain the value for thecorresponding PCMAX,c field from the physical layer.

In above example, Type 2 PHR is not reported whensimultaneousPUCCH-PUSCH for PCell is not configured, and PUCCH SCell isconfigured and deactivated.

An example procedure for reporting extended power headroom is shownbelow:

In an example embodiment, if the MAC entity has UL resources allocatedfor new transmission for this TTI the MAC entity may: if it is the firstUL resource allocated for a new transmission since the last MAC reset,start periodicPHR-Timer; if the Power Headroom reporting proceduredetermines that at least one PHR has been triggered and not cancelled,and; if the allocated UL resources can accommodate a PHR MAC controlelement plus its subheader if neither extendedPHR nordualConnectivityPHR is configured, or the Extended PHR MAC controlelement plus its subheader if extendedPHR is configured, or the DualConnectivity PHR MAC control element plus its subheader ifdualConnectivityPHR is configured, as a result of logical channelprioritization.

The MAC layer in the UE may instruct the Multiplexing and Assemblyprocedure to generate and transmit an Extended PHR MAC control elementfor extendedPHR2 according to configured ServCellIndex and the PUCCH(s)for the MAC entity based on the values reported by the physical layer.

Activation/Deactivation may be supported for PUCCH SCell. While thePUCCH SCell is deactivated in a PUCCH group, SCells belonging to thePUCCH group may not be activated. The eNB is supposed to manage theactivation/deactivation status. The eNB is supposed to deactivate anSCell when its PUCCH is remapped to a deactivated PUCCH SCell.

There may be two types of UE power headroom reports, Type 1 and Type 2.A UE power headroom PH may be valid for subframe i for serving cell c.

If the UE is configured with an SCG, and if a higher layer parameterphr-ModeOtherCG-r12 for a CG indicates ‘virtual’ for power headroomreports transmitted on that CG, the UE may compute PH assuming that itdoes not transmit a PUSCH/PUCCH on any serving cell of the other CG.

If the UE is configured with an SCG for computing power headroom forcells belonging to MCG, the term ‘serving cell’ may refer to a servingcell belonging to the MCG. For computing power headroom for cellsbelonging to an SCG, the term ‘serving cell’ may refer to a serving cellbelonging to the SCG. The term ‘primary cell’ may refer to the PSCell ofthe SCG. If the UE is configured with a PUCCH SCell for computing powerheadroom for cells belonging to a primary PUCCH group, the term ‘servingcell’ may refer to a serving cell belonging to the primary PUCCH group.For computing power headroom for cells belonging to a secondary PUCCHgroup, the term ‘serving cell’ may refer to serving cell belonging tothe secondary PUCCH group. The term ‘primary cell’ may refer to thePUCCH-SCell of the secondary PUCCH group.

An example Type 1 and Type 2 power headroom calculations is presentedhere. Example parameters and example calculation method is presented instandard document 3GPP TS 36.213 standard documents of the correspondingLTE release.

If the UE transmits PUSCH without PUCCH in subframe for serving cell c,power headroom for a Type 1 report may be computed using

PH _(type1,c)(i)=P _(CMAX,c)(i)−{10 log₁₀(M _(PUSCH,c)(i))+P _(O) _(_)_(PUSCH,c)(j)+α_(c)(j)·PL _(c)+Δ_(TF,c)(i)+f _(c)(i)}

[dB]

where, example P_(CMAX,c)(i), M_(PUSCH,c)(i), P_(O) _(_) _(PUSCH,c)(j),α_(c)(j), PL_(c), Δ_(TF,c)(i) and f_(c)(i) may be defined as follows.P_(CMAX,c)(i) may be the configured UE transmit power in subframe i forserving cell c and {circumflex over (P)}_(CMAX,c)(i) may be the linearvalue of P_(CMAX,c)(i). M_(PUSCH,c)(i) may be the bandwidth of the PUSCHresource assignment expressed in number of resource blocks valid forsubframe i and serving cell c. Po_PUSCH, c(j) may be configuredemploying RRC configuration parameters. If the UE is configured withhigher layer parameter UplinkPowerControlDedicated-v12x0 for servingcell c and if subframe i belongs to uplink power control subframe set 2as indicated by the higher layer parameter tpc-SubframeSet-r12. For j=0or 1, α_(c)(j)=α_(c,2)∈{0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1}. α_(c,2) isthe parameter alpha-SubframeSet2-r12 provided by higher layers for eachserving cell c. For j=2, α_(c)(j)=1. Otherwise: For j=0 or 1, α_(c)∈{0,0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1} may be a 3-bit parameter provided byhigher layers for serving cell c. For j=2, α_(c)(j)=1; PL_(c) may be thedownlink path loss estimate calculated in the UE for serving cell c indB and PL_(c)=referenceSignalPower−higher layer filtered RSRP, wherereferenceSignalPower is provided by higher layers and RSRP for thereference serving cell and the higher layer filter configuration for thereference serving cell.

Δ_(TF,c)(i)=10 log₁₀((2^(BPREK·K) ^(S) −1)·β_(offset) ^(PUSCH))

for K_(S)=1.25 and 0 for K_(S)=0 where K_(S) is given by the parameterdeltaMCS-Enabled provided by higher layers for each serving cell c. BPREand β_(offset) ^(PUSCH), for each serving cell c, are computed as below.K_(S)=0 for transmission mode 2; f(i) may be a function of power controlcommands.

PL_(c) is, for example, the downlink path loss estimate calculated inthe UE for serving cell c in dB and PL_(c)=referenceSignalPower−higherlayer filtered RSRP, where referenceSignalPower is provided by higherlayers. The UE may measure on or more pathloss values employing signalsreceived on one or more pathloss reference cells. A pathloss referencecell may be configured for a serving cell. The UE may calculate PL_(c)and may employ one or more pathloss values (PL_(c)) for calculation ofType 1 and Type 2 power headroom fields. If serving cell c belongs to aTAG containing the primary cell then, for the uplink of the primarycell, the primary cell may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP. For theuplink of the secondary cell, the serving cell configured by the higherlayer parameter pathlossReferenceLinking may be used as the referenceserving cell for determining referenceSignalPower and higher layerfiltered RSRP. If serving cell c belongs to a TAG containing the PSCellthen, for the uplink of the PSCell, the PSCell may be used as thereference serving cell for determining referenceSignalPower and higherlayer filtered RSRP. For the uplink of the secondary cell other thanPSCell, the serving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP.

The scheduling request (SR) is used for requesting UL-SCH resources fornew transmission(s). In DC, scheduling request (SR) may be directlytransmitted from UE to an SeNB via a PSCell. This may reduce schedulingdelay and related signaling load.

When PUCCH groups are configured, SR resources may be configured onPCell, PUCCH SCell, or both. The possibility to have SR resources inPUCCH SCell(s) may allow better distribution of SR load among theserving cells. In an example configuration, an SR for a UE may betransmitted on a serving cell, e.g. either on the PCell or on a givenPUCCH SCell. In some scenarios, there may be more capacity available onthe SCell, and this may be a reason to allocate more SR resources on anPUCCH SCell. If PUCCH on an SCell carries SR signals, the chance of a UEinitiated RA on the PCell due to a scheduling request may be reduced andsignalling overhead and RACH resource usage may be reduced.

In an example implementation, SR resources may be configured on PUCCHSCell and no SR resources may be configured on PCell. In an exampleimplementation, an SR load may be shared among a PUCCH SCell and aPCell. SR resources may be configured on both PCell and PUCCH SCell.Whether to configure SR resources on PCell, on the PUCCH SCell, or onboth PCell and the PUCCH SCell may be up to eNB and/or UEimplementation. SR resources may be configured on both PCell and PUCCHSCell. An SR_COUNTER may be increased when SR is sent on either PUCCHSCell or PCell and sr-ProhibitTimer may be implemented to control thetiming of SR transmission. An SR process may employ SR resources on botha PCell and a PUCCH SCell, when both resources are configured.

In an example implementation, SR resources may be interleaved in timedomain, for example, some subframes (TTIs) may include a valid SRresource on PCell, and some other subframes may include a valid SRresource on the PUCCH SCell. In an example, some TTIs may include avalid SR resource on the PCell, some TTIs may include a valid SRresource on the PUCCH SCell. In an example implementation, some TTIs mayinclude a valid SR resource on both PCell and PUCCH SCell. When SR isconfigured on both an activated PUCCH SCell and a PCell, the MAC entityuses whichever SR resources comes first. When SR is triggered, it may betransmitted on the first valid SR resource available, regardless ofwhether SR resources is on PCell or SCell. When SR is on PUCCH SCell,there may be gain in terms of load balancing by allowing transmission ofSR on an SCell. There may be some latency gain since there may be moreSR resources available on the SCell. The UE may choose the first SRresources available for transmission of an SR. In an example, a valid SRresource on PCell and PUCCH SCell may overlap in time. A TTI may notinclude any valid SR resource or include more than one valid SRresources (on both PCell and PUCCH SCell). An eNB may employ differentIEs for configuration of SR resources on PCell and PUCCH SCell. Exampleembodiments may be applicable to various SR configurationimplementations on PCell and PUCCH SCell.

In an example embodiment, SR resources may be configured by one or moreinformation elements in an RRC message. For example,SchedulingRequestConfig IE may be employed for configuration of PUCCHresources on the PCell and/or on a PUCCH SCell. TheSchedulingRequestConfig IE may be used to specify some of the schedulingrequest related parameters. The SchedulingRequestConfig IE may beincluded in a dedicated physical layer configuration IE of a UEconfiguration.

The SchedulingRequestConfig IE may comprise an information element toset up or release scheduling resources and other parameters.SchedulingRequestConfig IE may comprise PUCCH resource Index(sr-ConfigIndex), SR configuration index (sr-ConfigIndex), and SRmaximum transmission (dsr-TransMax) IEs. At least one RRC message mayinclude a first SchedulingRequestConfig IE for configuration of SRresources on PCell, and a second SchedulingRequestConfig IE forconfiguration of SR resources on PUCCH SCell. sr-ConfigIndex may bedefined and sr-PUCCH-ResourceIndex (e.g. sr-PUCCH-ResourceIndex,sr-PUCCH-ResourceIndexP1) may be defined. sr-PUCCH-ResourceIndex,sr-PUCCH-ResourceIndexP1 may be n_(PUCCH,SRI) ^((1,p)) for antenna portP0 and for antenna port P1 respectively. E-UTRAN may configuresr-PUCCH-ResourceIndexP1 if sr-PUCCHResourceIndex is configured.

At least one RRC message configuring SR configuration may also includesr-ProhibitTimer IE to be employed to determine a timer value forscheduling request processes.

When an SR is triggered, the corresponding SR process may be consideredas pending until it is cancelled. Pending SR(s) may be cancelled andsr-ProhibitTimer may be stopped when a MAC PDU is assembled and this PDUincludes a BSR (Buffer Status Report) which contains buffer status up to(and including) the last event that triggered a BSR, or when the ULgrant(s) can accommodate pending data available for transmission. If anSR is triggered and there is no other SR pending, the MAC entity may setthe SR_COUNTER to 0.

As long as one SR is pending, the MAC entity and if no UL-SCH resourcesare available for a transmission in this TTI, and if the MAC entity hasno valid PUCCH resource for SR configured in any TTI: UE (e.g. MACentity) may initiate a Random Access procedure on the SpCell and cancelpending SRs. In an example embodiment, if SR resources are configured ona PUCCH SCell and the PUCCH SCell is deactivated, the MAC entity may nothave a valid PUCCH resource for transmitting an SR signal on adeactivated PUCCH SCell. If SR resources is not configured on a PUCCHSCell, the MAC entity may not have a valid PUCCH resource for SR on thePUCCH SCell.

In an example embodiment, a UE may receive at least one RRC messagecomprising configuration parameters of one or more cells, the RRCmessage may comprise configuration parameters of scheduling requestresources and processes. At least one RRC message may comprise a firstSR maximum transmission information element (IE) for the PCell and asecond SR maximum transmission information element for the PUCCH SCell.The at least one message may comprise a common SR prohibit timerinformation element which is used for both PCell and PUCCH SCell.

The at least one message may comprise a first scheduling requestconfiguration index for scheduling request resources on the primaryPUCCH, if SR resources on PCell is configured. The first schedulingrequest configuration index may indicate a first scheduling requestperiod and a first offset. The at least one message may further comprisea second scheduling request configuration index for scheduling requestresources on the secondary PUCCH, if SR resources are configured for aPUCCH SCell. The second scheduling request configuration index mayindicate a second scheduling request period and a second offset.

In an example embodiment, an RRC message may comprise configurationparameters of SR resources on both a PCell and an SCell. In anotherexample embodiment, a first RRC message may configuration parameters ofSR resources on the PCell and a second RRC message may configurationparameters of SR resources on an SCell. The at least one RRC message maycomprise the first RRC message and the second RRC message.

At least one RRC message configuring SR configuration may also includesr-ProhibitTimer information element comprising a timer value forscheduling request processes. The value of IE sr-ProhibitTimer may be innumber of SR period(s). Value 0 means no timer for SR transmission onPUCCH is configured. Value 1 corresponds to one SR period, Value 2corresponds to 2*SR periods and so on.

At least one RRC message configuring SR configuration may also includedsr-TransMax IE in SchedulingRequestConfig IE. In an example embodiment,dsr-TransMax may take the value of n4, n8, n16, n32, or n64. The valuen4 corresponds to 4 transmissions, n8 corresponds to 8 transmissions andso on.

A UE may be configured by higher layers to transmit the SR on oneantenna port or two antenna ports of the serving cell with configuredPUCCH. The scheduling request may be transmitted on the PUCCHresource(s) n_(PUCCH) ^((1,{tilde over (p)}))=n_(PUCCH,SRI)^((1,{tilde over (p)})) for {tilde over (p)} mapped to antenna port p,where n_(PUCCH,SRI) ^((1,{tilde over (p)})) may be configured by higherlayers unless the SR coincides in time with the transmission of HARQ-ACKusing PUCCH Format 3 in which case the SR may be multiplexed withHARQ-ACK. The SR configuration for SR transmission periodicitySR_(PERIODICITY) and SR subframe offset N_(OFFSET,SR) may be defined bythe parameter sr-ConfigIndex I_(SR) given by higher layers. SRtransmission instances in a serving cell configured with SR are theuplink subframes satisfying

(10×n _(f) +└n _(s)/2┘−N _(OPFSET,SR))mod SR _(PERIODICITY)=0.

In an example embodiment, SR resources may be configured by eNB in a waythat TTIs with available SR resources in a PCell and an SCell do notoverlap. The time difference between two subsequent subframes with SRresources may be reduced when SR resources are configured on both PCelland PUCCH SCell.

When an SR is triggered, it may be considered as pending until it iscancelled. Pending SR(s) may be cancelled and sr-ProhibitTimer may bestopped when a MAC PDU is assembled and this PDU includes a BSR (BufferStatus Report) which contains buffer status up to (and including) thelast event that triggered a BSR, or when the UL grant(s) can accommodatepending data available for transmission. If an SR is triggered and thereis no other SR pending, the MAC entity may set the SR_COUNTER to 0.

In an example embodiment, whether to configure scheduling request onlyon PCell, only on the PUCCH SCell, or on both PCell and PUCCH SCell isup to eNB implementation. When SR is configured on both activated PUCCHSCell and PCell, the MAC entity may use whichever SR opportunity comesfirst for SR transmission. Based on the UE implementation, the MACentity may choose one of SRs when SRs are configured on PUCCH SCell(s)and PCell in the same TTI. In a MAC entity, there may be only onescheduling request procedure regardless of whether scheduling request isconfigured on multiple cells, e.g. one SR_COUNTER which is increasedwhen SR is sent on either PCell or PUCCH SCell and one sr-ProhibitTimer.

In a wireless device, as long as one SR is pending, and if no UL-SCHresources are available for a transmission in this TTI, and if the MACentity has no valid PUCCH resource for SR configured in any TTI:initiate a Random Access procedure and cancel pending SRs. In an exampleembodiment, if SR resources are configured on a PUCCH SCell and thePUCCH SCell is deactivated, the MAC entity may not have a valid PUCCHresource for SR on a deactivated PUCCH SCell. If SR is not configured ona PUCCH SCell, the MAC entity may not have a valid PUCCH resource for SRon the PUCCH SCell. If SR resources are configured on a PUCCH SCell andthe TAT associated with the TAG of the PUCCH SCell is not running, theMAC entity may not have a valid PUCCH resource for transmitting SR onthe PUCCH SCell. In an example embodiment, a PUCCH SCell has valid SRresources in a subframe, if SR is configured for the SCell in thesubframe, the PUCCH SCell is activated in the subframe, and the TATassociated with the TAG of PUCCH SCell is running in the subframe. IfTAT of a PUCCH SCell is expired, then PUCCH resources of the SCell isreleased and the PUCCH SCell is no longer considered an SCell withconfigured PUCCH and SR resources. SR resources may be configured for anSCell that is in a TAG that its TAT is not running. In such a case, theSCell does not have valid SR resources until the TAG is uplinksynchronized. When SR resources are not configured for a serving cell,that serving cell does not have valid SR resources.

The term eNB used in the various embodiments in this specification mayrefer to a base station in an LTE network or an enhanced LTE (eLTE)network or a 5G network.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the disclosure may also be implemented ina system comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this disclosure may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wireless device, configuration parameters indicating a mapping restriction, of a plurality of mapping restrictions, of a logical channel to one or more radio resource types of a plurality of radio resource types; triggering a buffer status report based on uplink data becoming available; receiving an uplink grant indicating radio resources of a radio resource type of the plurality of radio resource types; triggering a scheduling request in response to: the triggering the buffer status report; and the radio resource type not being of at least one first radio resource type, of the plurality of radio resource types, determined based on the plurality of mapping restrictions; and transmitting, by the wireless device, the scheduling request.
 2. The method of claim 1, wherein a logical channel scheduling request timer is not running when the scheduling request is triggered.
 3. The method of claim 1, wherein the mapping restriction indicates that first data of the logical channel can only be transmitted via the one or more radio resource types.
 4. The method of claim 1, wherein the mapping restriction indicates that: first data of the logical channel can only be transmitted via the one or more radio resource types; and the first data of the logical channel is not allowed to be transmitted on one or more second radio resource types of the plurality of resource types.
 5. The method of claim 1, wherein a logical channel is identified by a logical channel identifier.
 6. The method of claim 1, wherein the uplink data becomes available in the logical channel with a highest logical channel priority in a logical channel group.
 7. The method of claim 1, wherein a second mapping restriction of the plurality of mapping restriction maps the buffer status report to one or more first radio resource types of the plurality of resource types.
 8. The method of claim 1, wherein the radio resource type comprises at least one of: a licensed radio resource type; and an unlicensed radio resource type.
 9. The method of claim 1, wherein a second mapping restriction is configured for the buffer status report.
 10. The method of claim 1, wherein the buffer status report is a regular buffer status report.
 11. The method of claim 10, wherein the buffer status report is identified by a logical channel identifier.
 12. The method of claim 11, wherein a logical channel scheduling request timer is not running when the scheduling request is triggered.
 13. The method of claim 12, wherein the mapping restriction indicates that: first data of the logical channel can only be transmitted via the one or more radio resource types; and the first data of the logical channel is not allowed to be transmitted on one or more second radio resource types of the plurality of resource types.
 14. The method of claim 13, wherein the uplink grant indicates radio resources for new transmission.
 15. The method of claim 14, wherein configuration parameters indicate scheduling request resources.
 16. The method of claim 15, wherein the uplink data becomes available in the logical channel with a highest logical channel priority in a logical channel group.
 17. The method of claim 16, wherein the radio resource type comprises at least one of: a licensed radio resource type; and an unlicensed radio resource type.
 18. The method of claim 1, wherein the buffer status report is identified by a logical channel identifier.
 19. The method of claim 18, wherein a logical channel scheduling request timer is not running when the scheduling request is triggered.
 20. The method of claim 19, wherein the mapping restriction indicates that: first data of the logical channel can only be transmitted via the one or more radio resource types; and the first data of the logical channel is not allowed to be transmitted on one or more second radio resource types of the plurality of resource types. 